Design considerations

You can easily provision, configure and access the service Dynamic Server by using the DCS portal. There is no need for having a broad experience in using technical configuration tools, such as the vCloud Director. Swisscom recommends this product for creating simple solution designs with low requirements concerning network and firewall features.

NOTE: Exporting an existing Dynamic Server or migrating a Dynamic Server to a VM running in a Dynamic Data Center is not supported. Therefore, it is essential that you have a clear view of your projects goals. Choosing the wrong product at the beginning of a project can have significant impact on the effort to be spent for potential enhancements in the future.

Swisscom Dynamic Data Center is the more complex product that allows you to create comprehensive solution designs such as multi-tier architectures. It is suitable in cases with high requirements concerning networking and security features. You can order a DDC in two different flavours differing in the way the resources are assigned to the VMs running in it: The “Allocation Pool” model and the “Pay as you go” model.

The “Allocation Pool” model is based on a resource pool shared by all VMs running in the corresponding DDC. If you order a DDC and select the “Allocation Pool” model you will need to specify the amount of resources (CPU power, RAM and storage) that shall be available in this DDC.

Please see further details about CPU usage and dynamic resource allocation in Compute Power.

The picture below illustrates the interdependencies between the ordering and the billing process:

Interdependencies ordering & billing process

NOTE: Billing starts immediately for the resource pools you ordered, independent of whether there are any VMs created or running in the corresponding DDC.

The main difference of “Pay as you go” model compared to the “Allocation Pool” model is that resources are not provisioned in shared resource pools, but are assigned per VM. By ordering a DDC based on the “Pay as you go” model you can select the performance class of a vCPU. Please see further details about the vCPU performance class in Compute Power. In addition, you can optionally specify the maximum amount of Memory and Storage to be be available in this DDC.

Unlike the “Allocation Pool” model the cost of the “Pay as you go” model are not dependent on any ordered resource pools. The picture below illustrates the interdependencies between the ordering, configuration and billing processes.

Interdependencies ordering, configuration & billing process

Comparison of resource allocation models

"Allocation pool" model "Pay as you go" model
Pros
  • Overprovisioning of CUs is possible
  • variable vCPU power per VM
  • Cost for computing power and memory arises for running VMs only
  • Amount of CUs per vCPU is guaranteed
  • Ability to create elastic solutions (control cloud resources via API without the need to adapt resource pools)
Cons
  • Fixed cost based on configured resource pools (and not based on started VMs)
  • The CU resource allocation per VM depends on a workload calculation executed every 5 minutes
  • Performance issues (by agile workloads)
  • Overprovisioning is not possible
  • Requires more CUs depending on the Workload (and the performance class chosen)
  • Fixed vCPU performance class per DDC
Operation purpose This model is recommended for continuous workloads or workloads with low emphasis on performance This model is recommended for agile workloads with a strong emphasis on performance (e.g. for terminal servers)

results matching ""

    No results matching ""